home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC Shareware 1997 February
/
PC Shareware 1997-02.iso
/
programy
/
envlp122
/
envelop.3
/
Program
/
trouble.txt
< prev
next >
Wrap
Text File
|
1996-03-15
|
11KB
|
252 lines
The information in this file is taken from the Envelop Web site,
http://www.envelop.com, which may be more up-to-date than this file.
If you have a problem which is not described below or on our Web
troubleshooting page, please send e-mail to support@envelop.com.
TROUBLE SHOOTING (updated November 20, 1995)
1. What to do when Program Errors occur.
2. Stack error during startup.
3. Why do I have to register each time I download?
4. Error 102 during install.
5. The Controls palette is not visible on my screen.
6. Envelop doesn't start from the Program Manager under Windows NT.
1. What to do when Program Errors occur.
If Envelop encounters an internal program error, a message box is
displayed that contains an internal error code in the title bar, e.g
"10b1.bd82-00bc". If this happens, please note the code and the
circumstances and report it to us by sending us e-mail or using the
error-reporting facility on this site.
Envelop keeps a log in the file "envelop.log", located in the same
directory as the envelop.exe file (C:\ENVELOP\PROGRAM in a standard
installation), which contains time-stamped error codes. You may delete
this file if you wish; Envelop will start a new error log only if another
error occurs.
2. Stack error during startup.
SYMPTOM:
During startup, the Envelop splash screen shows, then the next
thing that happens is a message is displayed that Envelop caused
a stack error (sometimes this message is displayed more than
once) and the program exits.
DIAGNOSIS:
Under some system configurations, the Resize method of the
Envelop main form causes an infinite recursion which quickly
leads to a stack fault. The main one we know of is the selection
of "Large Fonts" instead of "Small Fonts" in the display settings
at certain resolutions. This error can occur under Windows NT
or Windows 95.
WORKAROUND:
There are two ways to work around this problem: modify your
display settings or modify the Resize method of the Envelop
main form.
To modify your display settings so Envelop can start up, either
start the Display Control Panel (NT) or click the right mouse
button on the desktop (Win95) and select Properties|Settings.
Then select "Small Fonts" in the "Font Size" combo box. You
may have to restart your computer for the change to take effect.
To modify the Resize method of the Envelop main form, first
change the display setting as described above so Envelop can
start up. Then edit the EnvelopForm (drag the Finger onto the
main form, or type "EnvelopForm" into the object selection
combo and press Enter, etc.). In the MethodEditor, select the
Resize method, and comment out or delete the following line of
code:
' Set the inside-height of the Form to be just shy [...]
' (hides border pixel).
Height = (Height - ScaleHeight) + toolbar.Height - 30
Check the method, and save the module: envelop.ebo, which
contains the EnvelopForm object. You can test that your change
is properly saved by re-starting Envelop and resizing the main
form. If the height does not "snap" back to just show the toolbar,
then the change is saved. Now you should be able to restore
your display settings and Envelop will start up without any
problem.
REPAIR:
The next upload of Envelop includes a modification of the code
that calculates Form.ScaleHeight. This change makes
ScaleHeight more accurate, and also makes the kind of
self-sizing done by the Envelop main form safer, thus preventing
this problem. The date for this upload has not yet been
determined.
NOTE:
Hearty thanks to Enveloper Philip Greer for bringing this
problem to our attention and helping so patiently and diligently
with the diagnosis.
If you see this problem due to circumstances other than the
display's font-size setting, please let us know.
3. Why do I have to re-register each time I download?
SYMPTOM:
Every time I come up to the Envelop site to get an updated
version, I have to fill the registration form out again. Why can't
you guys just remember it from last time?
REPAIR:
We changed the download form so that it now asks you for a
username and password. Your username and password must be
alphanumeric strings. Once you have registered with us once,
you will only need to supply your username and password in
order to access the download pages.
4. Error 102 during install.
SYMPTOM:
When the Envelop setup program is run, the following message
is displayed:
Setup is unable to find a compressed library file
required to proceed with the installation. Check to
make sure all required files are located with the setup
program. Error 102.
DIAGNOSIS:
Envelop requires Windows '95 or Windows NT 3.5 to install
and run correctly. This error is displayed when the setup
program is run under Windows 3.1 or Windows for
Workgroups.
REPAIR:
You must install Windows '95 or Windows NT before installing
Envelop.
5. The Controls palette is not visible on my screen.
SYMPTOM:
Envelop starts up OK, but I don't see the Controls palette, and
some of the other windows that I can see extend off the edge of
my screen. What now?
DIAGNOSIS:
Envelop versions prior to 1.0.2 start up with a screen layout
designed for a 1024x768 display resolution, and do not
automatically adapt to other screen resolutions. Depending on
the screen resolution, you may not be able to see the Controls
palette or the Object Viewer windows, and the Method Editor
and Debug windows may appear just at the very bottom of the
display. The Method Editor and Debug windows' title bars
might be obscured by the Windows '95 task bar if it is placed at
the bottom of your screen.
WORKAROUND:
The best way to work with Envelop through version 1.0.1 is to
set your display resolution to 1024x768. If this is not practical
or possible, you can work at lower resolutions by taking the
steps described below as needed for your display.
To get the Controls palette back on-screen, type this line of code
into the Debug window and press the Return (or Enter) key:
ControlTools.Palette.Left = 0
To get the Object Viewer back on-screen, type this line of code
into the Debug window and press the Return (or Enter) key:
ObjectViewer.Left = 0
You may then move the Controls palette and/or the Object
Viewer with the mouse and save their position by selecting
"File|Save All" from the main menu bar.
The Method Editor and Debug window always appear in the
same initial location on startup. If you are running at low
resolution under Windows '95 with the task bar displayed at the
bottom of the screen, you may not be able to see these windows.
One workaround is to change the task bar display to the top,
right or left of your screen by dragging it to the desired edge. Or,
you can set the Auto-hide property of the task bar by clicking the
right-mouse button on the task bar and selecting "Properties"
from the pop-up menu.
REPAIR:
Starting with version 1.0.2 (uploaded September 25) Envelop
has support for layouts for 640x480, 800x600, and 1024x768
built-in. You can also save custom tool layouts for those or other
resolutions.
6. Envelop doesn't start from the Program Manager under Windows
NT.
SYMPTOM:
Double clicking the Program Manager Icon for Envelop in the
Envelop group brings up the Envelop 1.0 splash screen, but it is
followed by an OK box announcing that Envelop has
encountered a segmentation violation. However, if I double
click the envelop.exe in the Envelop\Program directory,
Envelop starts up properly. What gives?
DIAGNOSIS:
Under certain conditions, the NT Envelop install fails to get
Envelop\Program into the path. As a result, when Envelop is
started in a directory other than Envelop\Program a needed DLL
is not being found. The segv occurs because, in this particular
startup case, we mis-handle the error from the OLE subsystem
that is trying to load the DLL. If Envelop is started from the
Program directory, that directory is implicitly "in the path" so
the DLL is found as expected.
WORKAROUND:
Put Envelop\Program in your path using the System icon in the
Control Panel.
REPAIR:
A new Install will be incorporated into the August 30th
distribution. That distribution will also handle the missing DLL
condition with a more informative error message.